What

It's much easier to debug the blueprint if we can see what's going on. Since the blueprint is just another store, we already have decent inspection tools for this.

This just adds a toggle to show the blueprint in the time panel and a bit of extra handling to resolve blueprint entity paths in the selection-panel.

This doesn't handle entity-path-collisions gracefully, but as a debug-only tool that seems like an acceptable trade-off. Eventually we are going to need to track the originating store as part of the selection anyways so this constraint should get resolved at that point.

This will become even more valuable as we migrate from serde-style to arrow-style blueprint components as the data UI will become much more useful.

Checklist

• I have read and agree to Contributor Guide and the Code of Conduct
• I've included a screenshot or gif (if applicable)
• I have tested demo.rerun.io (if applicable)
• The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG

• PR Build Summary
• Docs preview
• Examples preview
• Recent benchmark results
• Wasm size tracking